home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 9
/
Night Owl CD-ROM (NOPV9) (Night Owl Publisher) (1993).ISO
/
016a
/
sn_9304.zip
/
SN-RULES.SN
< prev
Wrap
Text File
|
1993-03-01
|
24KB
|
514 lines
┌─────────────────────────────────────────────────────┐
│ « SOURCENET: PREMIUM PROGRAMMING & E-MAIL NETWORK » │
└─────────────────────────────────────────────────────┘
Operational Guidelines
Copyright 1993, Rollin White
Release v1.11 dated 01/23/93
===========================================================================
Computer Education Services BBS : HOME OF SOURCENET
- 20222 Windcave Ln. -
- Huntington Beach, Ca. 92646-5341 -
BBS Line 1: 714-965-9963
Voice Line: 714-968-3143
FAX Line : 714-965-9963
Sysop: Rollin White
==========================================================================
* Marks items that are new or changed for V1.11 with the exception of
changing names of the Net Host and Network Administrator -rjw
--- RULES AND REGULATIONS REGARDING SourceNet ---
I. ADMINISTRATION.
1.0 The SourceNet International E-MAIL Network (hereafter referred
to as "Network", SourceNet Network or SourceNet) is a
telecommunications network comprised of one Central Host BBS,
Regional Hubs, Hubs, Nodes and points.
1.2 SourceNet is soley operated by Computer Education Services.
1.3 SourceNet is operated as a "public service" of Computer
Education Services and Computer Education Services BBS serves
as the Net Host BBS. The Network is run by the Network Administrator,
Rollin White, also the Sysop of Computer Education Services BBS.
1.4 The Network Administration reserves the right to admit or
refuse any BBS/SYSOP as participating members of the SourceNet
Network. The Network Administration further reserves the right
to remove and/or suspend Net Access of any individual node,
hub or regional hub for any action considered detrimental to
the goals, spirit and/or quality of the SourceNet Network, as
well as failure to abide by these guidelines.
1.5 Computer Education Services BBS is the Central Hub and Administrator.
Regional Hubs will send and receive mail through Computer
Education Services BBS. Local Hubs will transfer through their
Regional Hub. Nodes will transfer through their Local Hubs.
SourceNet will operate on .QWK/.REP or Fidonet Technology(FTN)
type mail transfer system.
1.6 SourceNet is provided "AS-IS" without warranty of any kind,
either expressed or implied, included but not limited to the
implied warranty of merchantability and fitness for a specific
purpose. The entire risk as to the quality and performance of
the Network or Software is with you. Should your Hardware or
Software prove defective, you assume the entire cost of all
necessary servicing, repair or correction. In no event will
the Network Administration or Computer Education Services be
liable to you for any damages, including any lost profits,
lost savings or other incidental or consequential damages
arising out of the use or inability to use this Network.
1.7 Pursuant to the Electronic Communications Privacy Act of 1986,
18 USC 2510 et. seq., all BBS SYSOPs and users participating
within SourceNet, must be aware that there are no facilities
provided by the Network for sending or receiving confidential
electronic communications.
Although SourceNet maintains the capability and capacity to
send and receive mail that is flagged as "Receiver-Only" or
"Routed Mail", mail so flagged is not to be considered by any
user as actual "private" messages.
The purpose of the "R/O", "Routed Mail" or "Point-to-Point"
flags are intended solely to provide a means to limit the
possible number of nodes and/or users that may have access to
the mail for display purposes.
--------------------------------------------------------------------------
II. NET HOST RESPONSIBILITIES.
2.1 Mail transfers will be conducted at least once within a
24-hour period for all Regional and Local Hubs. Nodes are
required to have a mail transfer at least every-other day, or
as requested by the users.
2.2 The Regional Hub will be responsible for maintaining all mail
flow between Local Hubs and help Local Hubs maintain all nodes
in their regions.
2.3 The Net Host BBS equipment is not the property of any system
relaying the SourceNet Network. No claims may be made against
the Sysop, the Software and/or Hardware that "comprises" the
Net Host System or BBS. All Software and Hardware required to
run the Net Host BBS is privately owned and used with
permission by the owners of the SourceNet Network
Administration and Computer Education Services.
2.4 SourceNet is a "NO-FEE" Network. This does not exclude
Regionals or Hubs from introducing a Cost Recovery System at
their own discretion.
--------------------------------------------------------------------------
III. NETWORK SOFTWARE.
3.1 Network members must use legally purchased or obtained Network
Software as defined by the respective Software author's
documentation. This includes registering shareware if used
beond its evaluation period.
3.2 The Network Administrator reserves the right to "decline or
terminate" access to the Network to those individuals failing
to operate with the properly registered or purchased software
used for netmail operations, and/or BBS operations.
--------------------------------------------------------------------------
IV. NETWORK SYSOP RESPONSIBILITIES.
4.0 All Hub Sysops will abide by administrative decisions in their
respective regions. Node Sysops will also be responsible for
abiding by the administrative decisions by said regions.
4.1 Hub Sysops must relay mail a minimum of once a day, unless it
is "technically impossible" to do so, or they have made prior
arrangements with the Network Administrator and their Regional
Hub.
4.1.1 Hub Sysops must not shut down for over 48 hours without
notifying the Network Administrator.
4.1.2 If a Hub Sysop does not relay for 4 days without
notification to the Network Administrator, its' Nodes and
Hub, the Hub may be removed at that region's Hub at the sole
discretion of the Network Administrator.
4.1.3 Hub SysOps should make "every possible effort" to
accommodate any/all conference requests for their nodes as
equipment/configurations allow. This applies to SourceNet
conferences only. This does not apply to any network
links.
4.1.4 When any Hub SysOp has been notified by the Network
Administrator to remove the net access of a node the Hub
SysOp should remove the node's access as soon as possible.
In the event that the Hub SysOp "does not" comply with a
"node-access-removal" request, the Hub SysOp's access may
be removed and the Regional "assignment" may be passed to
another.
4.1.5 The Hub SysOp has the "authority" to remove the access of
one or more of its nodes for two (2) days if the situation
warrants such an action. Immediately following any node's
"access removal", the Hub SysOp needs to notify the removed
node by voice and the Network Administrator via voice or
public message in NetAdmin explaining the situation in
full.
4.1.6 Regionals must relay through the Net Host BBS on a "daily
basis". Hubs must relay through their respective Regional on
a daily basis and Hubs cannot relay through the Net Host BBS
unless message activity from the Hub warrants more
"affordable" relays and upon approval by the Network
Administrator. Regional zoning isn't written in stone and is
flexible.
--------------------------------------------------------------------------
V. CONFERENCE MODERATORS.
5.1 Conference Moderators are to be selected by the Network
Administrator. Moderators may be removed or replaced should
the Moderator fail to follow the duties of that position.
5.2 Conference Moderator Duties:
5.2.1 Moderators _MUST_ abide by all SourceNet Network Guidelines
and Regulations. Moderators should report any situations to
the Network Administrator via the SN_NetAdmin conference.
5.2.2 Moderators should keep message traffic "on topic", while
directing off topic threads to their appropriate conferences.
5.2.3 Moderators are required to monitor the number of messages
incoming/outgoing in said moderated conference. When message
count becomes unsatisfactory, the Moderator should bring
this to the attention of the Network Administrator. If said
conference fails to be "profitable" for SourceNet, it is the
sole discretion of the Network Administrator to remove such
conference from the network.
5.2.4 Moderators must acknowledge their status as moderator in
said conference(s) by stating "SN-<conference> moderator" or
other such signature to be in the discretion of said
moderator.
5.2.5 Moderators are to assist members posting questions
concerning the subject matter of said conference. Problems
should be dealt with in the following matter:
a. Any moderator subjecting rules or regulations upon any
member of SourceNet _MUST_ quote said SourceNet rules and
regulations pertaining to the given offense. This is for
clarification to both user and moderator.
b. Issue polite warning to members failing to follow the
rules of said conference or Guidelines or Regulations of
SourceNet Network.
c. If member persists in said manner that said moderator
feels a temporary suspension is necessary, contact the
member's Sysop and the Network Administrator via the
SN_NetAdmin conference.
5.2.6 Moderaters should notify the Network Administrator of any
problems regarding duplicate mail or other conference Network
problem.
--------------------------------------------------------------------------
VI. CONFERENCE AND NETWORK BANS AND SUSPENSIONS
6.1 All suspensions or network bans are determined by the Network
Administration, the moderator, and the user's Sysop.
6.2 Moderators requesting administrative action must do so in the
SN-NetAdmin conference.
6.3 Upon network-wide suspension or ban, a SysOp may "appeal" the
decision on behalf of the user in the NetAdmin conference.
This may only take place after the suspension or ban has been
enforced by the SysOp. Upon conference suspension or ban the
user may appeal the decision directly to the Network
Administrator in the NetAdmin conference. This too may only
take place after conference suspension or ban has been
enforced.
6.4 Suspensions or bans are determined under the following
guidelines:
6.4.1 A warning message must come from the conference moderator
prior to administrative action unless actions are
determined to be severe, and/or blatant enough to warrant an
immediate suspension or ban as determined by the Network
Administrator.
6.4.2 2nd offense: 30 day suspension from conference with a 90
day probationary period.
6.4.3 3rd offense: If during probationary period, network-wide ban
for a period to be determined by the Network Administrator.
from the conference with a 90 day probationary period.
6.4.4 4th offense: Permanent network-wide ban.
6.4.5 Repeat offenses do not need to be the same nor do they need
to occur in the same conferences as the original offense.
6.4.6 The Administration reserves the right to determine if the
actions of a user warrant a conference suspension or
network-wide suspension.
6.4.7 All temporary suspensions are for a period of no less than
30 days unless otherwise shortened by the Network
Administration. Any/all probationary terms are for a period
of no less than 90 days unless otherwise shortened by the
Network Administration.
--------------------------------------------------------------------------
VII. SOURCENET NETWORK GUIDELINES
7.1 While it is not the intent of SourceNet or the Network
Administrator to interfere with any Sysops authority on his or
her own BBS, all relayed conferences are subject to the
jurisdiction of these guidelines. These Network guidelines
are explained in detail below and SourceNet Network SysOps are
responsible for the enforcement these Network guidelines.
7.2 Participating SourceNet Network SysOps will not relay nor
will allow to be relayed messages that contain information
that advertise BBS's un-less in the SourceNet Network BBS AD
Conference. The placement of BBS telephone numbers
within messages to advise users of a contact telephone number
is not considered a "BBS Ad" as long as the intent of the
message is clearly evident without the telephone number. It is
understood that a user might disregard this rule. It is the
expectation of the Network Administrator that SysOp's will
take appropriate action to prevent this occurrence. Flagrant
disregard of this rule justifies the removal of that node
from the Network. It's also understood that if an ad is
relayed and the SysOp corrects the situation, it does not
justify removal of that node from the Network.
7.3 No Flames or Personal Attacks. Anyone found to be abusive in
nature, such as but not limited to, name calling, insults,
slanderous statements, arrogant or instigative posts or any
other rude, lewd or otherwise obnoxious behavior or comments,
is to be removed from the conference. Further occurances of
this abuse will result in the user(s) being removed from the
Network completely.
No "offensive or abusive" language is to be used in any and
all of the SourceNet conferences. The use of any word, group
of words, expression, comment, suggestion, or proposal which
is profane, filthy, lewd, lascivicious, obscene, indecent, or
that is demeaning ethnically or racially is strictly
prohibited within the SourceNet Network. Network member SysOps
must remove any users from the echoes for flaming and/or
fighting. We cannot ask that users be removed as "users of
your board" but if they are a problem to SourceNet they must
not have access to it.
SourceNet prohibits profanity, race bashing, sex
discrimination, or crude remarks on a persons ability or
knowlege. SourceNet is specifically designed for the
programmer, and all those echoing SourceNet should encourage
its users to participate in the conferences.
SourceNet, T&G Computers Inc and all member SysOps assume no
accountability or liability whatsoever for any violations of
this policy by any and all users of the SourceNet Network.
Network SysOps can and will be held accountable for failure to
remove any user or users who make statements that are abusive,
slanderous or demeaning to any individual, group,
organization either social, political, theological or racial.
7.4 Any illegal activities, including but not limited to the
promotion of illegal acts and promotion of software copyright
infringement will not be allowed within the SourceNet Network.
Any such activities constitute a grievous reason for the
removal of the node or hub from the Net, and may necessitate
compensatory action against the violator for any legal
liabilities such activities may cause the SourceNet Network.
7.5 Aliases are not allowed through SourceNet.
SourceNet strictly prohibits the use of aliases anywhere in
SourceNet conferences. SourceNet allows sysops to have aliased
users - however, aliased users must _NOT_ be allowed on _ANY_
of SourceNet Network's conferences.
The definition to SourceNet of an alias is a name used by a
caller whose intent is to prevent identification of the caller
by the Sysops or any other SourceNet Network member.
Sysops carrying SourceNet Network are responsible for ensuring
that only validated users are allowed access to SourceNet
Network. It is the Network Administrator's
understanding that each node SysOp is responsible for the
names used on their own BBS.
Aliases granted by Sysops for security reasons are exempt from
said above guideline.
7.6 Signatures and Taglines.
Taglines and/or signatures should be kept under 3 lines. No
sigure and/or tagline may reflect a moderator, host or
administrative position outside of the SourceNet Network
Positions. Conference Moderators should display their
moderative signatures only in conferences they moderate.
7.7 Quoting Guidelines.
No fancy quote utilities are allowed throughout SourceNet
Network. These cause SourceNet overhead and subsequent expense
to those Sysops relaying the mail. Fancy quotes consist of any
text quoted with a "border" consisting of more than a single
ascci line around the quoted portion of a reply. While this
can be abused there are limitations to all kinds of quotes.
Quote side will consist of the quoted text and the board to
the quoted portion. Quotes are not to exeed the portion of the
message. Please quote only when necessary. Conference moderators
will be responsible for policing over quoting and ASCII boxes.
7.8 Ansi Graphics are permitted only in the SourceNet ANSI/BBSAD
conference and nowhere else.
--------------------------------------------------------------------------
VIII. SOURCNET NETWORK CONFIGURATION.
8.0 Monitoring SN_Admin.
SourceNet member Sysops _MUST_ monitor SN_NetAdmin on a timely
basis to be awware of announcements, conference additions or
delitions, or mail regarding configurations. Sysops must
"correct" any detrimental activity coming into the SourceNet
Network via their board -on a timely basis- including, but not
limited to the following: duplicates, cross-echos, abusive
users and improper or excessive taglines. All Hubs must ensure
that their nodes take corrective action against these or other
problem areas.
8.1 SourceNet Network Logo or "Tagline".
Each and every SourceNet Network tagline must begin with the
text string "SourceNet". QWK format members must have the
string "SourceNet" in their "TAG" or "HTAG" portion of their
Network configuration files. Fidonet Technology members must
include the string "SourceNet" in their origin lines.
--------------------------------------------------------------------------
VIX. SOURCENET CONFERENCE CONFIGURATION.
9.1 Required Conferences.
SN-HUB is SourceNet's Administrative conference and is
required to be carried by all members.
9.2 The "Moderators" conference is open only to Hosts or
Moderators or the Sysop "carrying" SourceNet. It is the sole
use of the Moderators conference to discuss situations between
members of SourceNet - without interference from those members.
9.3 The SN-Net_Admin conference is open to ALL users of the SourceNet
network, and is a public forum for users to take part in NETWORK wide
discussions and for complaints. This is a required conference and is to
be made public.
9.4 General SourceNet Conferences.
All remaining SourceNet conferences are considered public
access and accessible to everyone. The exception here is if
the user has been "removed" from an SourceNet conference for
any valid reason (as decided by the Network Administrator,
the users SysOp and Conference Host or Moderator or these
SourceNet Network guidelines section 6.0)
SysOps will make their users aware of any conferences "not
carried". This can be done by means of news screens or
bulletins. Also, if you are carrying multiple networks, your
conference menu must display a type of coding that
differentiates our conferences from any of the other network
conferences that you might also have available.
9.5 SourceNet Network related discussions or business will be
discussed in the SourceNet SN_NetAdmin conference. If such
discussion should develop elsewhere, move the thread into the
SN_NetAdmin conference.
9.6 New conferences will be added at the sole discretion of the
Network Administrator. Conference suggestions should be posted
in SN_NetAdmin so that SysOps and users may discuss the idea.
--------------------------------------------------------------------------
X. SOURCNET AMENDMENTS AND ADMINISTRATION BREAKDOWN.
10.1 The Network Administrator is responsible for implementing any
changes to these regulations and guidelines.
Any SourceNet Network Node or Hub Sysop, Host or Conference
Moderator may request amendments to these regulations and
guidelines in the SN_NetAdmin conference.
All discussions regarding SourceNet Network policy,
guidelines, regulations, and/or other Network business must be
discussed in the SN_NetAdmin Conference.
10.2 SourceNet Administrative Breakdown:
┌─────────────┐
│ADMINISTRATOR│
└──────┬──────┘
┌─────────┴────────┐
│BOARD OF DIRECTORS│
└─────────┬────────┘
┌───┐ ┌─┴─┐ ┌───┐
│# 1├───────────┤# 2├──────────┤# 3│
└───┘ └─┬─┘ └───┘
┌─────────┴────────┐
┌──────────────┤AUXILARY POSITIONS├────────────┐
│ └─────────┬────────┘ │
│ │ │
┌────┴─────┐ ┌──────┴────┐ ┌─────────┴───────┐
│MODERATORS│ │NEWS LETTER│ │CLASS INSTRUCTORS│
└──────────┘ └───────────┘ └─────────────────┘
---------------------------------------------------------------------------
XI. INFORMATION CONCERNING BASNet ECHO MAIL NETWORK
11.0 BASNet is soley operated by Ken Prevo, and the Host system is
the ToolKit BBS. SourceNet is making BASNet available to all users
of SourceNet, and HUB, Local HUB and Node are resposible for
following BASNets administrative guidlines. These very much parallel
SourceNets. SourceNet is in no way responsible for information given
or recieved via BASNet. HUBS carrying BASNet are required to seperate
them from SourceNet by a preseding BN-, so as not confuse it with
SourceNet.
*XII. ADMISSIONS
12.0 Admissions policy is intended to be simple and quick. A
prospective node wishing to join SourceNet should send his
application as a file to one of the following people:
1. The Network Administrator
2. The nearest Hub
3. The Hub he/she wishes to receive mail from
At that point the node may arrange for mail transfers to begin
with the hub of his choice. Note that this is a provisional
admission. Final admission requires the Network Administrator's
approval.
12.1 It is the duty of all hubs and regionals to forward
applications sent to them to the Network Administrator.
==========================================================================